Add Fault Injection from Behavior Tree Specification #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nfigured probability)
|
@rodrigoqueiroz I didn't see before that there were conflicts between this PR and the master. But since you havent been using the delay and error for fault injection, will you even merge them? (this might introduce conflicts with the fix naming PR, please let me know if I can help later on) |
|
Abandoning these changes as out of date. An example of changing the BTree grammar. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added two forms of fault injection from Behavior Tree Specification:
Probability of inverting the signal returned from the condition testing.
How to configure? One can configure the probability by setting a variable error in a node Condition.
ex.: condition lc( sim_time (repeat=False, tmin=3, tmax=10), error=0.1)
Which means that there is a 10% chance of returning an inverted result for the sim_time condition checking.
Introduced delay on checking the condition.
How to configure? One can configure the probability by setting a variable delay (in sec) in a node Condition.
ex.: condition c_busy_lane( lane_occupied(), delay=3 )
This simulates that the driver is taking at least 3 seconds to check if the next lane is busy.
Obs. the total time to check for a condition is then the delay + the checking algorithm processing time.